| 1. | Read uncommitted ? permits dirty reads but not lost updates
未授权读取允许脏读取，但不允许更新丢失。 |
| 2. | Specifies that dirty reads are allowed
指定允许脏读。 |
| 3. | This can only be used for systems that can operate with dirty reads
此隔离级别只能用于能对脏读进行操作的系统。 |
| 4. | This prevents dirty reads
这样可以避免脏读。 |
| 5. | Dirty read : thread one writes data ; thread two reads what thread one wrote
线程1写入了数据，线程2读取了线程1所写入的数据。 |
| 6. | Incorrect concurrency can lead to problems such as dirty reads , phantom reads , and non - repeatable reads
不正确的并发可能导致脏读、幻读和不可重复读等问题。 |
| 7. | A dirty read is possible , meaning that no shared locks are issued and no exclusive locks are honored
可以进行脏读，意思是说，不发布共享锁，也不接受独占锁。 |
| 8. | When this option is set , it is possible to read uncommitted modifications , which are called dirty reads
设置此选项之后，可以读取未提交的修改，这种读取称为脏读。 |
| 9. | Which will not allow a value to be accessed until after it has been committed , and which will forbid dirty reads
，这使得在提交值之前，不允许对它进行访问。并且禁止脏读。在 |
| 10. | Isolation levels are described in terms of which concurrency side effects , such as dirty reads or phantom reads , are allowed
使用允许由并发产生的副作用（如脏读或幻读）来说明隔离级别。 |
